The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Code using user-defined data structures
|
|
Design, define and use data structures that are aggregate of other data types Completed |
Evidence:
|
Code using array of user-defined data types Completed |
Evidence:
|
Use facilities in language to create, manipulate and destroy dynamic variables such as arrays Completed |
Evidence:
|
Code using standard algorithms
|
|
Use modular programming approach to coding, including pass-by-reference parameter passing Completed |
Evidence:
|
Write code to create and manipulate 2-D array Completed |
Evidence:
|
Create and maintain sorted array and use language-provided facilities for sorting array of ordered elements Completed |
Evidence:
|
Code simple binary search technique for use with array of sorted data Completed |
Evidence:
|
Code binary file-handling solutions using random-access algorithms Completed |
Evidence:
|
Debug code
|
|
Use stand-alone debugging tools or tools provided by integrated development environment (IDE) to debug code Completed |
Evidence:
|
Use debugger to trace code execution and examine variable contents to detect and correct errors Completed |
Evidence:
|
Document activities
|
|
Follow organisational guidelines for developing maintainable code and adhere to provided coding standard when documenting activities Completed |
Evidence:
|
Apply internal documentation, suitable for use by peers, to all code created Completed |
Evidence:
|
Use documentation tools available in target language when documenting activities Completed |
Evidence:
|
Test code
|
|
Design and document tests Completed |
Evidence:
|
Undertake limited testing of produced code to ensure compliance with program specification Completed |
Evidence:
|
Capture and record test results Completed |
Evidence:
|
Create application
|
|
Build application in response to user requirement Completed |
Evidence:
|
Access multiple source-code files Completed |
Evidence:
|
Employ IDE project maintenance facilities or make files to automate program building Completed |
Evidence:
|
Develop program specification solution when provided with basic design document Completed |
Evidence:
|
Design algorithm and document, construct and test applications in response to problem description using target language Completed |
Evidence:
|
Document completed application Completed |
Evidence:
|